Agenda:

• Talk about software development services, architecture, and plan for upgrades and deployment

Attendees:

• Todd Ruston
• Cathy Sewell
• Pat Allen
• Pete Braccio
• Duane Edgington
• Karen Salamy
• Kevin Gomes

Notes

• Security
  • Kerberos
  • Centrify
  • LDAP
    • SSDS is the outstanding issue with security. 6 shares on tornado that have wide open permissions. ssdsdata. auvctd, Work with Cathy on mapping all this out and getting permissions resolved.
    • new-ssds needs to be re-opened.
    • SSH integration for kerberos is a piece of cake in centrify.
    • Kerberos is THE goal.
• Database
  • All apps move to Equinox? Yes 2008. (or solstice).
• Upgrades:
  • We should make sure we address the AD groups used in JIRA confluence.
  • RHEL 6 is released. RHEL 5 is supported for 7 years so we will go with that for now.
  • Crowd (#1)
  • Confluence (#3)
  • JIRA #2
  • Alfresco #4
  • Subversion #5
  • SSDS (#1?)
• Future Installations:
  • Bamboo, Fisheye, Crucible (#2) - CANON
  • Messaging (RabbitMQ)

1. Other
   1. lack of planning
   2. lack of specificity of how things talk through firewall. build internally and then move to Dmz in emergency. research/engineering not following deployment instructions to deploy experiments on mars. Network plan. MARS is an NSF facility. MARS Is different from DMZ, more complex.
   3. Non-standard and then dump on I.S. to fix.
   4. standardizing stacks for J2EE stack (application stacks).
   5. embedded systems: not really
   6. So much is deployed in the experimental state. Then it stays that way. Maintenance is a nightmare.
   7. How does I.S. tell when something is working or not. SNMP, ports, nagios. What is actually not working, not just my server is broken
   8. even if it is just showing them visibly.
   9. Who manages patches for non-standard installs.
   10. Been bit by lock down to particular versions because of bugs. We are using the bug and so we can't patch.
   11. Some cases where we don't patch because it breaks development process.
   12. How to we budget for maintenance.
   13. I.S. feels you must patch.
   14. Timeliness of patching.